Columbia Kermit/kermit.zip/newsgroups/misc.19960715-19961006/[e-mail] _Sat Aug 31 11:17:55 1996.msg

Internet Message Format | 2020-01-01 | 4KB

Return-Path: [e-mail]
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30]) by watsun.cc.columbia.edu (8.7.5/8.7.3) with ESMTP id LAA25680 for <[e-mail]>; Sat, 31 Aug 1996 11:17:55 -0400 (EDT)
Received: (from news@localhost) by newsmaster.cc.columbia.edu (8.7.5/8.7.3) id LAA00514 for kermit.misc@watsun; Sat, 31 Aug 1996 11:17:54 -0400 (EDT)
Path: news.columbia.edu!sol.ctr.columbia.edu!spool.mu.edu!howland.erols.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: [e-mail] (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MSK3.14, Windows, and 3COM ethernet
Message-ID: <[e-mail]>
Date: 31 Aug 96 08:33:13 MDT
References: <505ku0$[e-mail]> <[e-mail]> <507f3h$[e-mail]>
Organization: Utah State University
Lines: 72

In article <507f3h$[e-mail]>, [e-mail] (David S Cargo) writes:
> In article <[e-mail]>,
> Joe Doupnik <[e-mail]> wrote:
>>In article <505ku0$[e-mail]>,
>> [e-mail] (David S Cargo) writes:
>>> After not being able to achieve stable operation with the packet driver
>>> and Kermit with DOS, I switched to using the ODI drivers with DOS,
>>> which has worked reliably.  I decided to try running with windows using
>>> the following setup.  The first two lines I run from the batch file;
>>> I need them to use Kermit from DOS.  The next two lines I typed by hand.
>>> They seemed to work, but when I connected to the router at the other end
>>> of my ethernet cable, it had not received any ethernet packets.  It's
>>> working under DOS (which is how this message is getting sent).
>>>
>>> Any suggestions on how the find and fix the problem are welcome.
>>>
>>> David S. Cargo ([e-mail])
>>>
>>> @echo off
>>> REM  Netware startup
>>> if not exist C:\NWCLIENT\lsl.com goto noNetware
>>> if not exist C:\NWCLIENT\ipxodi.com goto noNetware
>>> rem if not exist C:\NWCLIENT\vlm.exe goto noNetware
>>> C:\NWCLIENT\lsl.com
>>> C:\NWCLIENT\3C5X9.com
>>> rem C:\NWCLIENT\ODIPKT 0 96
>>> rem C:\NWCLIENT\WINPKT 0x60
>>> rem C:\NWCLIENT\ipxodi.com
>>> rem C:\NWCLIENT\vlm.exe
>>> rem f:\login
>>> rem c:
>>> rem goto doneNetware
>>> :noNetware
>>> rem echo Netware client software missing, Netware not started
>>> :doneNetware
>>------------
>>    I'm a little confused. The above works fine at DOS level, I infer,
>>but if you then start Windows (version??) it does not, correct? If so then
>>the obvious suggestion is to look for conflicts over the hardware,
>> particularly
>>the IRQ (probably overlaps a serial or parallel port). Don't forget about
>>Plug&Play upsetting the 3Com board.
>>    Joe D.
>
> Let me be more clear; I had to run quick to fold some laundry in the middle
> of the message.
>
> I'm running DOS 6.22 or Windows 3.1.  There's no Windows 95 and no
> Plug&Pray involved.  I don't think I have any port conflicts.
>
> Running lsl and 3com5x9 lets me run Kermit 3.14 from DOS over Ethernet
> without problem.  Reading setup.doc led me to conclude that I should
> be able to run Kermit 3.14 from Windows if I also ran odipkt and
> winpkt.  So I tried it using this batch file and then running the
> remarked out lines for odipkt and winpkt by hand, and then starting
> Windows.
>
> According to a Windows inspection program, winpkt was running at
> software interrupt 0x60, just like it was supposed to.  But, when
> I opened a MS-DOS prompt and ran Kermit, no Ethernet traffic was
> being generated.  (At least according to the router at the other end,
> which I could reach just fine using DOS.)
>
> So, what might I be doing wrong.  The setup.doc is less than clear
> on this point, in terms of complete examples.
--------
    What you've done is fine, so far as can be judged from afar. My
suggestion is there could be a conflict between your Ethernet board and
Windows, a non-Kermit item, such as the common IRQ 4/3 situation where
Windows thinks they are for the serial ports and takes them over.
    Joe D.